Closed
Official
Online
03.16.2022 12:00 +0000
04.30.2022 12:00 +0000
Can you please list CPU, Socket, Motherboard that are allowed for submissions for each Challenger 2022 Div I,II, III, ect, ect. Thank You :-)
Any specific reason why ?
It says max clock 5206. I set my multiplier to 52 and my clock gets detected at 5220 and even 5230. Does that mean I need to fuck with my bclk and adjust multiplier down because if it does maybe we could consider the variances for different motherboards/bioses out there next time? Also, if it turns out you really have to change your bclk instead of doing an easy 52x I assume the top two results are already considered invalid?
if it mentions higher clocks in XTU , you should bring it down to maybe 99.8 and run it.... no consideration required from our side, that's up to you to do...
thank you for clarification
also, based on what I just saw disappear - including my own submission is it also not a good idea to change CPU to "12900k (8P)" if disabling e-cores is better for us?
What is the point of running hwinfo64 if XTU reads a different clock speed?
I'll just submit one and if it disappears I'll assume the answer is no I shouldn't do that.
This is so strange but XTU keeps reporting 5.22 even thought CPU-Z shows 5198 to 5200. Once it locks into thinking you have 5.22 even if I change the BCLK on the fly and lower it to 99.0 it stays at 5.22. WTF?!?! Anyone seen this problem? Which program will be trusted in the screenshot?!?
Same, xtu always report 5.22.... my score also deleted. I think on my screen also hwinfo was shown and it report max 5200. So we need to run 5.1 go get 5.12. Think all other clocks get up to 5.22 maybe? Bench again cause xtu is weird ?. Will try in the evening.
I'll raise the cpu speeds to 5220 for XTU stage
Bless you oh Capital L Double E Big freakin' G... BLESS YOU!
I believe leaving it auto on the Apex means that it the AI overclocking system can do funky stuff to it, right? But the answer is no - I haven't tried that. I would think that forcing it 100 would acceptable... But you never know with BIOS quirks. I'll try it next time I'm in this situation.
and turning of spread spectrum might be an idea too
any ideas what's causing the xtu monitoring to be off by several hundred MHz im my case?
also why is the score always getting devided by 8, no matter how many cores are enabled? shouldn't it be 16 then for the 12900K?!
12900K(8P) : 8 cores (E cores disabled)
12900K: 16 cores
If you disable cores HWBOT doesn't take it into account, it's either divided by 8 or 16....
So then this stage implies "all P cores enabled" because there is no 12900K(2P)? or is it allowed to set the CPU to G7400 so the calculation is actually done based on 2 P cores enabled?
Nope one doesn't submit a 12900K with 2P cores enabled as a G7400... you want to compare apples with oranges, if we would allow this, the entire database will become a shitshow
Either you use all cores of your 12900K or you use only the 8P .... It can't get more simple than that...
Mhh i use 8 cores in my xtu run but score is deleted, but why? U said use 8 P cores, i did. Where is the Problem?
I have no clue what you are talking about:
https://hwbot.org/submission/4973172_snakeeyes_xtu_2.0_core_i9_12900kf_7320_marks
You ran 8P AND 8E cores enabled = 16 cores, so the score should be divided by 16...
I deleted an older and lower score sub (7240 score on 12900KF)... if that is what you mean maybe?
Ok, but this isnt 8P but i only ise 8 Pcores for this run ?. I can Show in a Video, only 8 cores running in xtu. Why it is for 16 cores? So at least u delete my highest 8P.
CPUZ states you have all E cores enabled, so it's a 16 core run. Even if you set affinity to 1 core, it is still a 16 core CPU handling things albeit on one core...
Log in or register to comment